Fix FB CLI scrape-interval and podman @user-password test failures - #1062
Merged
Conversation
Serialize the two PMM server containers in docker-compose-scrape-intervals and add explicit readyz healthchecks so FB CLI pmm-client docker runs do not fail when both servers compete for resources on CI runners. Co-authored-by: davi.travaglia <davi.travaglia@percona.com>
travagliad
marked this pull request as ready for review
July 9, 2026 14:08
kiranvuyurru
approved these changes
Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
FB PR #4465 (
PMM-15129) failed two pmm-qa checks:@user-passwordpodman e2e — apt install failed withlibncurses5/libtinfo5404 on Ubuntu 22.04 jammy mirrors (infra/setup bug, not a product issue).pmm-client dockerCLI —docker-compose-scrape-intervals.ymlstarted two PMM Server containers in parallel; on resource-constrained CI runners one server (pmm-server-scrape-interval) timed out its healthcheck while the other became healthy.How
apt-get update, replace unavailablelibncurses5withlibncurses6, remove broken emptyapt-get installstep inrunner-e2e-tests-podman.yml./v1/server/readyzhealthchecks with a 60s start period, and makepmm-server-custom-scrape-intervalwait forpmm-server-scrape-intervalto be healthy before starting — serializing the two heavy server startups.FB staging values used for triage
PMM_SERVER_IMAGE:perconalab/pmm-server-fb:PR-4465-80972d9PMM_CLIENT_VERSION:https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4465-80972d9.tar.gz